| From: | Joseph Duchatelet |
| Date: | 1 May 2000 at 14:51:17 |
| Subject: | Re: oktagon.device & NSDPatch |
On 01-May-00, Dirk Neubauer wrote:
>Hi Joseph!
HI Dirk, thanks for your reaction
>On 30-Apr-00, you wrote:
>> According to my documentation i can start this file from CLI, putting the
>> "oktagon" file in the expansion drawer of my boot medium. and having
>> "Binddrivers" in my startup sequence.
>You have to disable the boot rom on your oktagon, too. Use Oktagonprefs for
>that
>reason.
In a recent mail i explained my progress (?) with NSDPatch.
I did check oktapussy and in the doc, which describes 4 methods to use the new
driver.
1) Method 1: run the new driver from 'expansion'. (Here it is said that you
should disable the controller's rom.) This is the preferred way if you boot
from a different controller.
This is not my case, i think, my boot partition is on a HD physically mounted
on the oktagon controller.
When i try to save the 'disabled' condition OktagonPrefs tells me that i will
only be able to boot from floppy. This is not what i want.
2) load the driver from CLI or WB if you use the controller only occasionally,
disable the controller:
not my case, i tested this anyhow (controller disabled 'use', not 'save'" and
was not confident the new oktagon devices were present (scsi.device had same
version as before, oktagon.device still present in memory)
3) Making the driver reset resident. The old (ROM) driver is not disabled. ( I
like that)
I did try to use this. oktagon.device was not present any more, (expected
that, since the doc states that oktagon.device is replaced by 'a' scsi.device)
scsi.device however had still the same version 43.34 (12/21/99)- as before
(did not expect that, this one being the standard OS.35 scsi.device's
versionnr, but then i i don't understand too much about this )
"NSDQuery scsi.device" gave me
OpenDevice("scsi.device", 0, ior, 0x00000000) was successful (Version 109.3)
io_Device: 0x0021172C, io_Unit: 0x00215338
Error 110 while trying NSCMD_DEVICEQUERY: MAGIC_ERROR_110: not really a new
style device - strange query answer.
io_Actual is 0.
I do note an other version number here (created by oktagon ? ) ??)
Do you have the same response ?
4) Loading the driver out of the Rigid-Disk-Blocks
I could use this too. But that will be for later. Enough problems for now.
5) combine 3 & 4
idem
What do you use ? Why ?
I also noted that the "oktagon" driver in 'oktapussy' is newer than in the
latest HDInstTools. Its 'version' states
"SoftSCSIOktagonC9X 9.9 (11/24/1998) ,
the only other date string it contains is:
SoftSCSI_OktagonC9X (Oktagon SCSI) 9.9 (24.11.98)
The HDInstTools oktagon file returns as ' version'
"OktagonMount 6.10 (08/15/1995)" but contains also the strings
SoftSCSIOktagonC9X 6.9 (31.08.95)
oktagon.device 6.10 (26.08.95)
So i was wrong in my previous mail on the subject :
oktagon.device 6.8 appears only in my rom device.
I guess to make the oktagon.device 6.10 work i need to have a new rom.
As the NSDPatch i used for the oktagon.device 6.8 seemed to work i may stay
with this solution or go on & use Oktapussy which allows me to update
'oktagon' without a new rom, but for which NSDPatch is not fully happy yet.
I do not really understand what NSDQuery does, nor how you can exploit its
result to create an appropriate NSD patchline.
I read its doc & the NSDPatch.cfg file but still..
Thanks for any help or comment
Joseph
------------------------------------------------------------------------
Shower mom with love & roses!
FREE bouquet of chocolate roses with Mother's Day purchase.
Plan ALL your celebrations in one place at GreatEntertaining.com.
Click now.
http://click.egroups.com/1/3527/2/_/644178/_/957203702/
------------------------------------------------------------------------